feat: create op-simulator as basic proxy #33
Conversation
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @tremarkley and the rest of your teammates on |
tremarkley
changed the title
tremarkley
changed the title
tremarkley
changed the title
tremarkley
force-pushed
the
harry/op-simulator
branch
2 times, most recently
from
efda568 to
06f4cd4
Compare
tremarkley
force-pushed
the
harry/op-simulator
branch
6 times, most recently
from
762d86b to
5c0d8af
Compare
tremarkley
force-pushed
the
harry/op-simulator
branch
from
5c0d8af to
39f92ae
Compare
| } | ||
|
|
||
| type Supersim struct { | ||
| log log.Logger | ||
|
|
||
| l1Chain *anvil.Anvil | ||
| l2Chains map[uint64]*anvil.Anvil | ||
| l1Anvil *anvil.Anvil |
There was a problem hiding this comment.
Nice work!
In order to simplify the changes in this file, I wonder if we should simply have OpSimulator manage the lifecycle of the the underlying chain, in this case anvil. So that we dont need reference to each individual pieces here
Not worth addressing in the PR. Just some food for thought for ways to clean up this code in the future
There was a problem hiding this comment.
Sounds good, I wont address in this PR, since I want to keep this change small.
If we want to stick to the original design, we should create an Orchestrator service that handles spinning up all the anvil instances and OpSimulator instances.
tremarkley
force-pushed
the
harry/op-simulator
branch
from
39f92ae to
7247db8
Compare
tremarkley
force-pushed
the
harry/op-simulator
branch
from
7247db8 to
f2cc9a8
Compare
Closes #16
This PR makes the following changes:
op_simulatorpackageop_simulatorfor each chain as a ReverseProxy that intercepts all rpc requests and forwards them to the underlying anvil node for that chainop_simulatorandanvilinstances using thesupersimpackage